Setting up remote compile and debug

Specifying the platform settings
To compile and debug remotely you must specify the platform specific settings in the Preferences. To do so:

- Choose Tools > Preferences....
The Preferences tool opens.

Specific Settings for remote compile and debug

In the Platform List, select a target platform or create a new one.
Select the Remote Settings tab.
In the Host field, enter the name of the target machine.
By default, the number of seconds reserved for Remote Shell Script Execution is specified. If the scripts need more time to execute, increase the number of seconds in the Wait _ Seconds for Shell to Become Ready field or vice-versa.
By default, the local user name is used for remote connections. If you will login to the target machine using a different user name, enter this user name in the User Name field.

| Note
| Entries in the User Name field are case sensitive.

6. If you are using SNiFF+'s Make Support, in the Remote Host SNIFF_DIR field, enter the directory where SNiFF+ is installed on the target machine.

General settings for compiling and debugging

Select the Debugger tab.
In the Debugger view, choose a debugger adaptor from the Adaptor drop-down.
SNiFF+ automatically fills in the Executable and Prompt fields. Modify these fields if necessary.
Select the Make Support tab.
The SNiFF+ platform settings, the Make command and the Platform Makefile are already defined. If you use a different Make system and/or Platform Makefile, enter the appropriate settings in the Make Command field and/or Platform Makefile field. For new platforms, enter the appropriate platform settings.
Press OK to apply the settings and to close the Preferences.

Specifying a different remote Shell executable
By default, SNiFF+ is configured to use rlogin for remote compilation.
If you want to use a different remote Shell executable on Unix:

In the Preferences, under the Tools node select the Shell view.
In the Local Executable for Remote Shell field, enter the name of the Shell executable.
Press OK to close the Preferences.

| On Windows
| We do not recommend Windows users changing the rlogin.exe entry in the Local Executable for Remote Shell field because this rlogin entry has been especially adapted for remote compile and debug.

Assigning platforms to SNiFF+ working environments
You can assign platforms to Shared Object Working Environments (SOWEs) and to Private Working Environments (PWEs), because Make can only be started in these working environments.

- Choose Tools > Working Environments.
The Working Environments tool opens.

Assigning a platform to a new working environment

In the Working Environments tool, select the Shared Source Working Environment (SSWE) or the root node if you want to create a PWE.
Choose Edit > New Shared Object or Edit > New Private. A dialog opens.

3. In the Working Environment field, enter the name of the working environment.
4. In the Root field, specify the root of the working environment as you would access it from the host machine.
5. In the Root on Remote Host field, specify the root of the working environment as you would access it from the target machine.

   | Caution
   | Do not use any environment variables or any shell metacharacters to specify the path name.

   In a Unix -- Unix work situation, you can create symbolic links to access the working environment root directory so that it looks the same from both machines. In this case, leave the Root on Remote Host field blank.

   | Note
   | Root on Remote Host is disabled when you don't have a SNiFF_CROSS or a SNiFF_EVAL license, please refer to Licensing.

6. In the Platform drop down, select the remote platform.
7. Press Ok to close the New Private / New Shared Object dialog.
8. In the Working Environments tool, choose File > Save to save the changes to the Working Environments.

Assigning a platform to an existing working environment
You can assign a platform to your Private Working Environment and to the Shared Object Working Environment.

Select a working environment and choose Context menu > Modify....
The Modify dialog appears.
In the Root field of the Modify dialog, specify the root of the working environment as you would access it from the machine that you are currently working on.
In the Root on Remote Host field, specify the root of the working environment as you would access it from the target machine.

| Caution
| Don't use any environment variables or any shell metacharacters to specify the path name.

In a Unix -- Unix work situation, you can create symbolic links to access the working environment root directory so that it looks the same from both machines. In this case, leave the Root on Remote Host field blank.

| Note
| Root on Remote Host is disabled when you don't have a SNiFF_CROSS or a SNIFF_EVAL license, please refer to Licensing

4. In the Platform drop down, select the remote platform.
5. Press Ok to close the Modify dialog.
6. In the Working Environments tool, choose File > Save to save the changes to the Working Environments.

Invoking Remote Compile and Debug
Now that you have set all the relevant settings for remote compile and debug, you can go ahead and open your project, either in your Private Working Environment or in the Shared Object Working Environment. Before compiling, remember to update Makefiles. When you compile and debug the project, SNiFF+ uses the information in the Platform view of the Preferences. This allows you to compile and debug remotely using the commands in the Project Editor's Target menu.